Requirements for SDSS Data Management Systems

This document describes the functional specifications on the SDSS Science Archive, which is to develop into the public data archive.

The data management systems shall maintain all processed data from the SDSS and provide access by SDSS scientists and operators in order to maximize the ease of the following:

  1. Operate the SDSS survey so as to maximize the efficiency of operations.
  2. Perform Quality Analysis operations on the data so as to ensure its integrity. The operations will verify calibrations, target selection criteria and classifications, completeness and accuracy.
  3. Provide SDSS scientists with access to the data and tools to permit selection of spectroscopic targets for certain categories (serendipity; stars).
  4. Provide SDSS scientists with access to the data so as to enable scientific analyses.

Requirements for the Science Archive

The science archive shall consist of:

  1. A science database that shall:
  2. A set of files tracked by the science database.
  3. A set of files not tracked by the science database.

Input to Science Archive

  1. Survey Definition
  2. Final Astrometric Calibration
  3. Final Photometric Calibraton
  4. Merged Object Lists
  5. Target Selection
  6. Spectroscopic Pipeline
  7. Enhanced goal: Scientist derived catalogs
  8. Enhanced goal: Other input catalogs
  9. Separate files tracked from Science Database
  10. Separate files not tracked or accessible from Science Archive

Functional Goals

  1. User will be able to carry out efficient queries to locate objects over one or more ranges of following attributes:
  2. User will be able to carry out queries on any retained object parameter (subject to implementation constraints).
  3. Enhanced Goal: All calibrated quantities can be recomputed using improved astrometric and photometric calibrations. Queries can be performed on the recalibrated quantities.
  4. For all efficient queries, return an esimated number of objects to be located.
  5. For all located objects, users shall be able to specify an arbitrary subset of stored parameters to be returned (subject to implementation constraints) plus the following derived quantities:
  6. Users shall be able to perform the following functions:

Technical Goals

  1. User interface
  2. Distributability
  3. Security